home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Base Documentation 1998 November
/
IRIX 6.5.2 Base Documentation November 1998.img
/
usr
/
share
/
catman
/
u_man
/
cat1
/
pmnsadd.z
/
pmnsadd
Wrap
Text File
|
1998-10-20
|
5KB
|
132 lines
PPPPMMMMNNNNSSSSAAAADDDDDDDD((((1111)))) PPPPMMMMNNNNSSSSAAAADDDDDDDD((((1111))))
NNNNAAAAMMMMEEEE
ppppmmmmnnnnssssaaaadddddddd - add new names to the Performance Co-Pilot PMNS
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
////uuuussssrrrr////ppppccccpppp////bbbbiiiinnnn////ppppmmmmnnnnssssaaaadddddddd [----dddd] [----nnnn _n_a_m_e_s_p_a_c_e] _f_i_l_e [ ... ]
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
ppppmmmmnnnnssssaaaadddddddd adds subtree(s) of new names into a Performance Metrics Name
Space (PMNS), as used by the components of the Performance Co-Pilot
(PCP).
Normally ppppmmmmnnnnssssaaaadddddddd operates on the default Performance Metrics Namespace
(PMNS), however if the ----nnnn option is specified an alternative namespace is
used from the file _n_a_m_e_s_p_a_c_e.
The default PMNS is found in the file /_v_a_r/_p_c_p/_p_m_n_s/_r_o_o_t unless the
environment variable PPPPMMMMNNNNSSSS____DDDDEEEEFFFFAAAAUUUULLLLTTTT is set, in which case the value is
assumed to be the pathname to the file containing the default PMNS.
The new names are specified in the _f_i_l_e, arguments and conform to the
syntax for PMNS specifications, see ppppmmmmnnnnssss(4). There is one PMNS subtree
in each _f_i_l_e, and the base PMNS pathname to the inserted subtree is
identified by the first group named in each _f_i_l_e, e.g. if the
specifications begin
myagent.foo.stuff {
mumble 123:45:1
fumble 123:45:2
}
then the new names will be added into the PMNS at the non-leaf position
identified by myagent.foo.stuff, and following all other names with the
prefix myagent.foo.
The new names must be contained within a single subtree of the namespace.
If disjoint subtrees need to be added, these must be packaged into
separate files and ppppmmmmnnnnssssaaaadddddddd used on each, one at a time.
All of the files defining the PMNS must be located within the directory
that contains the root of the PMNS, this would typically be ////vvvvaaaarrrr////ppppccccpppp////ppppmmmmnnnnssss
for the default PMNS, and this would typically imply running ppppmmmmnnnnssssaaaadddddddd as
root.
Provided some initial integrity checks are satisfied, ppppmmmmnnnnssssaaaadddddddd will update
the PMNS using ppppmmmmnnnnssssmmmmeeeerrrrggggeeee(1) - if this fails for any reason, the original
namespace remains unchanged.
The ----dddd option allows the resultant PMNS to optionally contain duplicate
PMIDs with different names in the PMNS. By default this condition is
considered an error.
PPPPaaaaggggeeee 1111
PPPPMMMMNNNNSSSSAAAADDDDDDDD((((1111)))) PPPPMMMMNNNNSSSSAAAADDDDDDDD((((1111))))
CCCCAAAAVVVVEEEEAAAATTTT
Once the writing of the new _n_a_m_e_s_p_a_c_e file has begun, the signals SIGINT,
SIGHUP and SIGTERM will be ignored to protect the integrity of the new
files.
FFFFIIIILLLLEEEESSSS
/_v_a_r/_p_c_p/_p_m_n_s/_r_o_o_t the default PMNS, when then environment variable
PPPPMMMMNNNNSSSS____DDDDEEEEFFFFAAAAUUUULLLLTTTT is unset
SSSSEEEEEEEE AAAALLLLSSSSOOOO
ppppmmmmnnnnssssccccoooommmmpppp(1), ppppmmmmnnnnssssddddeeeellll(1), ppppmmmmnnnnssssmmmmeeeerrrrggggeeee(1) and ppppmmmmnnnnssss(4).
PPPPaaaaggggeeee 2222